Dynamics GP End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Dynamics GP versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Dynamics GP 18 (Modern) is supported until April 30, 2031, its end-of-support date. Active support for Dynamics GP 18 (Modern) ends on December 31, 2029; security fixes continue until that end-of-life date. The next Dynamics GP version to reach end of life is 2018 R2, on January 11, 2028. 6 of 9 tracked Dynamics GP versions are past end of life; the most recent to reach it, 2016 R2, did so on July 14, 2026. The full Dynamics GP lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2013 | — | Mar 12, 2013 | Apr 11, 2023 | 1278 days past EOL | EOL |
| 2013 R2 | — | Aug 21, 2014 | Apr 11, 2023 | 1278 days past EOL | EOL |
| 2015 | — | Feb 18, 2015 | Apr 8, 2025 | 550 days past EOL | EOL |
| 2015 R2 | — | Aug 30, 2015 | Apr 8, 2025 | 550 days past EOL | EOL |
| 2016 | — | May 1, 2016 | Jul 14, 2026 | 88 days past EOL | EOL |
| 2016 R2 | — | Dec 1, 2016 | Jul 14, 2026 | 88 days past EOL | EOL |
| 2018 | — | Dec 1, 2017 | Jan 11, 2028 | 458 days remaining | Active |
| 2018 R2 | — | Oct 2, 2018 | Jan 11, 2028 | 458 days remaining | Active |
| 18 (Modern) | — | Oct 7, 2019 | Apr 30, 2031 | 1663 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/microsoft-dynamics-gp)
Dynamics GP lifecycle status — the real story
Dynamics GP is Microsoft's on-premises accounting and ERP product. Releases up to Dynamics GP 2018 R2 follow the Fixed Lifecycle Policy, each with its own mainstream and extended support dates.
Since October 2019 Dynamics GP, version 18.x, follows the Modern Lifecycle Policy: customers stay supported by taking at least one of the updates Microsoft releases each June, October and December. Installing any compatible tax release or hotfix on GP 2018 or GP 2018 R2 moves that installation onto the Modern Lifecycle Policy. Microsoft has set a retirement date for Dynamics GP itself, after which product enhancements, tax updates and technical support stop; Microsoft says security updates, if needed, will continue for a limited period after that. For version 18, support is that retirement date and eol is the end of the security-update window, both as Microsoft states them on its Dynamics GP lifecycle page.
Microsoft encourages Dynamics GP customers to move to Dynamics 365 Business Central. A GP installation that skips the yearly updates falls outside the Modern Lifecycle Policy before the product's own retirement date.
Dynamics GP release and support pattern
Of the 9 release lines tracked, 6 are past end of life and 3 are still within support. The newest line, 18, was released October 7, 2019. The next scheduled end of life is 2018-r2 on January 11, 2028 — 458 days from this build. The longest-supported line currently published is 18, to April 30, 2031.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Dynamics GP end of life mean for your organization?
When a version of Dynamics GP reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Dynamics GP should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Dynamics GP reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Dynamics GP versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Dynamics GP has 6 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Dynamics GP is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."